Skip to content

Update to pythresh v1#684

Open
KulikDM wants to merge 1 commit into
yzhao062:developmentfrom
KulikDM:fix/update-to-pythresh-v1
Open

Update to pythresh v1#684
KulikDM wants to merge 1 commit into
yzhao062:developmentfrom
KulikDM:fix/update-to-pythresh-v1

Conversation

@KulikDM
Copy link
Copy Markdown
Contributor

@KulikDM KulikDM commented May 15, 2026

All Submissions Basics:

  • Have you followed the guidelines in our Contributing document?
  • Have you checked to ensure there aren't other open Pull Requests for the same update/change?
  • Have you checked all Issues to tie the PR to a specific one?

All Submissions Cores:

  • Have you added an explanation of what your changes do and why you'd like us to include them?
  • Have you written new tests for your core changes, as applicable?
  • Have you successfully ran tests with your changes locally?
  • Does your submission pass tests, including CircleCI, Travis CI, and AppVeyor?
  • Does your submission have appropriate code coverage? The cutoff threshold is 95% by Coversall.

Hi, this commit aligns PyOD with PyThresh V1, making it a standard that aligns better with the Sklearn and PyOD API having fit and predict functions. Documentation has been updated and two new thresholders have been made available.

Note, that the minimum requirement for using PyThresh in PyOD is now V1 but the benefits (able to threshold on test data correctly with respect to train data) outweighs the downsides. Older versions of PyOD will still work with the new PyThresh but not vice versus.

Hope you are happy with this commit and that it makes PyOD even better than it already is!

@KulikDM KulikDM changed the title fix: update to pythresh v1 Update to pythresh v1 May 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant